home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Diamond Collection
/
The Diamond Collection (Software Vault)(Digital Impact).ISO
/
cdr49
/
ngwmfc.zip
/
README.MFC
< prev
next >
Wrap
Text File
|
1995-01-10
|
21KB
|
612 lines
THE GROUPWISE MESSAGE FILE CONVERSION NLM
The GroupWise Message File Conversion NLM (referred to as MFC
NLM; its file name is NGWMFC.NLM) overcomes the file format
differences that exist between WordPerfect Office 3.1 and Novell
GroupWise 4.x systems. This NLM also provides the following
benefits:
■ Increases the speed of message conversion
■ Lets you use the GroupWise NLM and OS/2 Message Servers
■ Provides seamless two-way message conversion
PREREQUISITES
Before you install the MFC NLM you must have already
interconnected the WordPerfect Office 3.1 and Novell GroupWise
4.x systems. For detailed instructions about interconnecting the
two systems, see:
Connecting GroupWise 4.1 and WP Office 3.1 Systems in the
GroupWise Administration Guide.
You must also be able to run the WP Office 3.1 Admin program.
The following NetWare NLMs must be loaded prior to loading the
MFC NLM:
CLIB
STREAMS
NGWLIB
NGWMSIP
AFTER311
SNMP
TLI
You do not have to reload these NLMs if they are already loaded.
Use NetWare's MODULES console command to see which NLMS are
already loaded. You may want to load these NLMs from
AUTOEXEC.NCF.
INSTALLING THE MFC NLM
You must perform the following tasks to install the MFC NLM:
■ Create the directory structure in the 4.x domain directory
■ Copy the NLMS to SYS:SYSTEM
CREATING THE DIRECTORY STRUCTURE
The director y structure the MFC NLM uses to route messages must reside
in the 4.x domain structure. When you installed GroupWise, the \WPGATE
directory was added as part f the domain file structure. This directory
is reserved for GroupWise Gateways. The GroupWise Admin program treats
the MFC NLM as a gateway. For this reason you must use the DOS MD
command to append the following subdirectories to the \WPGATE directory:
\WPGATE
\MFCGW
\LOG
\PROBLEM
\LIN
\MF
\TEMP
\LIN_MF
\MF_LIN
\TRANSIN
COPYING THE MFC NLM TO SYS:SYSTEM
NetWare must first know where the NLM resides. By default, NetWare looks
to the SYS:SYSTEM directory for all NLMs. For this reason, copy the
following files to the SYS:SYSTEM directory on the server where the NLMs
will be loaded.
NGWMFC.NLM
STARTUP.MFC
If you choose not to copy the files to SYS:SYSTEM, you must either
include the pathname where the MFC NLM is located in the search path,
or type full pathname when loading the NLM.
After you created the directory structure and copied the NLM to the
SYS:SYSTEM directory, you must configure the GroupWise 4.x system
and the WP Office 3.1 system. Proceed to the next section for more
information.
CONFIGURING THE GROUPWISE 4.X SYSTEM
To configure the MFC NLM you must use the Admin program to:
■ Define the NLM as a gateway
■ Alter the GroupWise 4.x link to the WP Office 3.1 system
■ Alter the WP Office 3.1 link to the GroupWise 4.x system
To define the MFC NLM as a gateway,
1 Start the Admin program.
2 Choose the domain the MFC NLM will service. This is the domain where
you created the MFC subdirectories.
3 Choose CREATE from the File menu, then choose GATEWAY to display
the Gateway Information dialog box.
4 Fill in the fields:
GROUPWISE NAME (required): Enter a name you will use to identify
the MFC NLM.
FOREIGN NAME: This field is not used by the MFC NLM.
DESCRIPTION: (Optional): Enter descriptive information, such as
the date the NLM was installed, who installed it, the connecting
WP Office 3.1 Transfer Host, or any other pertinent information.
DIRECTORY: Choose this field to display the Installed from this
list.
GATEWAY ALIAS TYPE: This field is not used by the MFC NLM.
EXECUTION MODE: Choose STAND-ALONE.
TIME ZONE: Choose this option to set the time zone for the MFC NLM.
ADMINISTRATOR: The options in this menu do not apply to the MFC NLM.
TIME: The options in this menu do not apply to the MFC NLM.
OPTIONAL: Choose this option to display the Optional only ones that
apply to the MFC NLM:
LOGGING LEVEL: Use this field to control the amount of information
displayed on the MFC NLM Operation screen. This field sets the
default for the NLM; however, the logging level can be altered
using the /loglevel startup switch or the Logging Level option
in the MFC NLM interface. The logging levels are:
■ OFF: This option disables the logging feature.
■ NORMAL (Default): This option provides general informational
messages.
■ DIAGNOSTIC: This option provides more detail than the Normal level.
■ VERBOSE: This option logs all NLM activity but also requires more
network resources.
MAX LOG AGE: This option lets you set how many days the log files
are stored until they are automatically deleted. The default is
7 days.
LIMIT DISK USE: This option sets the total amount of disk space
log files can occupy. The default is 1024K or 1M.
5 Press OK at the Optional Gateway Settings dialog box to return to the
Gateway Information dialog box.
6 Press OK at the Gateway Information dialog box to return to the System
window.
You are now ready to proceed to the next section for information about how
to alter the links between the WP Office 3.1 and GroupWise 4.x systems.
ALTERING THE GROUPWISE 4.X LINK
To alter the GroupWise 4.x link,
1 From the System Window, choose the domain where the MFC NLM resides.
2 Choose EDIT from the Actions menu to display the Domain Information
screen.
3 Choose MESSAGE SERVER CONFIGURATION to display the Message Server
Configuration dialog box.
4 Choose NETWORK LINKS to display the Network Links dialog box.
5 Choose the WP Office 3.1 domain from the list, then choose EDIT LINK
to display the Define Domain Connection dialog box.
6 Choose GATEWAY as the link type to display the Gateway Link dialog box.
7 Fill in the fields:
LOCAL GATEWAY: If the MFC NLM is the only gateway, it will
automatically appear in the field. If not, choose this field to
display the gateway list, then choose the MFC NLM.
GATEWAY ACCESS STRING: This field does not apply to the MFC NLM.
RETURN LINK: Enter the name of the WP Office 3.1 Transfer Host that
links to the GroupWise 4.x system.
8 Choose OK to return to the Network Links dialog box.
9 Choose CLOSE to return to the Message Server Configuration dialog box.
10 Choose OK to return to the Domain Information dialog box.
11 Choose OK to return to the System Window.
ALTERING THE WP OFFICE 3.1 LINK TO THE GROUPWISE 4.X SYSTEM
Before WP Office 3.1 messages can be converted, you must alter the
Transfer Host's link to the GroupWise 4.x system.
To alter the WP Office 3.1 link,
1 Change to the WP Office 3.1 Administration directory.
2 Type OFFADMIN and press Enter to display the Office System
Administration menu.
3 Choose Using Office Notebook (N) to display the Office
System Admin (Notebook) menu.
4 Choose Host Notebook (H), then enter the name of the path to
the HOSTID.NB file when prompted. The list of all your
WP Office 3.1 hosts is displayed.
5 Select the Transfer host you use to connect to the GroupWise 4.x
system, then choose Edit to display the WordPerfect Office Host screen.
6 Tab down to the HOST DIRECTORY field. The path in this field should
be pointing to the domain directory of the GroupWise 4.x system.
7 Alter the path to point to the \WPGATE\MFCGW directory you created
earlier.
8 Save the changes and return to the Office System Admin (Notebook)
screen.
9 Run GENOFF from the Office System Admin (Notebook) screen to update
the databases for each host.
10 Exit the Admin Program.
At this point the MFC NLM is linked to the WP Office 3.1 and
GroupWise 4.x systems. Proceed to the next section for instructions
about loading the MFC NLM.
LOADING THE MFC NLM
You can load the MFC NLM:
■ Manually at the NetWare console
■ Manually at the NetWare console using a startup file
■ Automatically through AUTOEXEC.NCF
Regardless of how you choose to load the NLMs, you must first be familiar
with the NLM's startup switches.
STARTUP SWITCHES
The MFC NLM uses a series of startup switches to provide the NLM with
vital information. Some of the switches are required; others are optional.
The list below defines each startup switch.
@
Use this switch to point to a startup file for loading the MFC NLM.
Do not add a space between the @ pointer and the startup file name.
Syntax: load ngwmfc @[server/volume:]filename
Sample: load ngwmfc @server1/vol1:startup.mfc
/home (Required)
Use this switch to point the MFC NLM to the location of the \WPGATE\MFC
directory. This directory should be a subdirectory of the GroupWise 4.x
domain directory structure. If the GroupWise 4.x domain resides on a
different file server, you must include the file server and volume name
in the syntax. You must also use the \USER and \PASSWORD switches.
Syntax: /home-[server/volume:]path
Sample: /home-server1/vol1:headq\wpgate\mfcgw
/31transin (Required)
Use this switch to point to the location of the WP Office 3.1 primary host's
transin directory.
If the WP Office 3.1 system resides on a different file server, you
must include the file server and volume name in the syntax. You must
also use the \USER and \PASSWORD switches.
Syntax: /31transin-[server/volume:]path
Sample: /31transin-server1/vol1:office30\transin
/logpath
Use this switch to point to the location where the log files are stored.
If the log files are stored on a different server, you must include the
server and volume names. The directory \wpgate\mfcgw\log is the default.
Syntax: /logpath-[server/volume:]path
Sample: /logpath-server1/vol1:log
/31pull
Use this switch when you are connecting to a VAX system. The VAX cannot
place messages in the MFC NLM's directory structure. Instead, the
Message Server must pull the messages from the VAX. Enter the location
of the VAX pull directory.
Syntax:/31pull-[server/volume:]path
Sample:/31pull-server1/vol1:\31domain\to_pc\transin
/scancycle
Use this switch to set the number of seconds the NLM scans its
directories to convert messages. The default is 60 seconds.
Syntax: /scancycle-[seconds]
Sample: /scancycle-300 (5 minutes)
/logdiskoff
Use this switch to turn off disk logging. The default is On.
Sample: /logdiskoff
/loglevel
Use this switch to control the level of logging information the NLM
displays. The options are Diagnostic, Verbose, Normal, and Off. The
default is Normal.
Syntax: /loglevel-[level]
Sample: /loglevel-diagnostic
/logdays
Use this switch to designate how many days to keep log files on disk.
The files are deleted if they exceed this number of days.
The default is 7 days.
Syntax: /logdays-[number of days]
Sample: /logdays-5
/user
Use this switch to set the NetWare user ID for accessing remote file
servers. When the WP Office 3.1 or GroupWise 4.x systems reside in
different file servers, you must create identical user accounts of each
server to give the NLM access. Each account must have identical
mappings, rights, and password.
Syntax: /user-[user ID]
Sample: /user-bob
/password
Use this switch to set the password for accessing remote file servers.
See /user for more information.
Syntax: /password-[password]
Sample: /password-mfc
/help
Use this switch to display the online startup switch help screen.
This will not load a functioning NLM.
THE STARTUP FILE
The startup file is a text file that stores all the switches used by the NLM.
If you use the startup file, you do not have to type each switch and its
value at the system console when you load the NLM. An example of the default
startup file is found below.
; Sample NGWMFC startup file
; ===========================
; Use this file to store switch settings for the MFC NLM. Remove
; the semicolon from the line below the word EXAMPLE, and replace
; the sample settings with your network settings.
;THE FOLLOWING SWITCHES ARE REQUIRED.
; HOME points the NLM to the path of the gateway directory
; Syntax: /HOME=[server/volume]:path
; Example: see below
; /home=server1/vol1:\domain1\wpgate\mfcgw
; 31TRANSIN points the NLM to the path of the 3.1 \TRANSIN
; directory. You must include \TRANSIN at the end of the path.
; Syntax: /31TRANSIN=[server/volume]:path
; Example: see below
; /31transin=server1/vol1:\31domain\host6\transin
; =============================================================
;THE FOLLOWING SWITCHES ARE OPTIONAL.
; 31PULL points to the path of the 3.1 pull directory instead of
; using the MFCGW\TRANSIN. Required for VAX hosts.
; Syntax: /31PULL=[server/volume]:path
; Example: see below
; /31pull=server1/vol1:\31domain\to_pc\transin
; LOGPATH points to the path of the log file directory.
; Default:\mfcgw\LOG\
; Syntax:/LOGPATH=[server/volume]:path
; Example: see below
; /logpath=server1/vol1:\nlmlogs\mfcgw
; USER is a NetWare user ID. Required if connecting to other
; servers. User ID must be common for all connected servers.
; Syntax: /USER=NetWare User ID
; Example: see below.
;/user=mfcuser
; PASSWORD is the NetWare password of the user ID of the /USER
; switch. Required if /USER is used.
; Syntax: /PASSWORD=NetWare password
; Example: see below
; /password=resucfm
; SCANCYCLE specifies how often the NLM scans for messages.
; Default: 60 seconds
; Syntax: /SCANCYCLE=number of seconds
; Example: see below
; /scancycle=300
; LOGLEVEL specifies the level of details for screen and disk
; logging. Levels include: Off, Normal, Verbose, and Diagnostic.
; Default: Normal
; Syntax: /LOGLEVEL=level
; Example: see below
; /loglevel=verbose
; LOGDISKOFF turns off disk logging. Screen logging is controlled
; by /LOGELEVEL.
; Default: ON
; Syntax: see below
; /LOGDISKOFF
; LOGMAX Specifies maximum disk space allowed for log files.
; Default: 1024 kilobytes
; /LOGMAX=number of kilobytes of space
; Example: see below
; /logmax=2048
; LOGDAYS specifies the number of days log files are stored.
; Default: 7
; Syntax: /LOGDAYS=number of days
; Example: see below
; /logdays=21
; end of file.............
=================================================================
Before you use the startup file, edit the switch values to reflect your
network's configuration. Use a semicolon to disable a switch or to add
comments.
MANUALLY LOADING AT THE NETWARE CONSOLE
To load the MFC NLM from the console prompt, NetWare must first know where
the NLM resides. By default, NetWare looks to the SYS:SYSTEM directory for
all NLMs. If the NLM is not found there, NetWare checks all search paths.
You may also choose to include the full pathname where the MFC NLM resides.
This points NetWare directly to the proper location.
Syntax: load [server/volume:]ngwmfc /home-[path] /31transin-[path]
Sample: load server1/vol1:mfc\ngwmfc /home-server1/vol1:headq\wpgate\mfc
/31transin-server1/vol1:office31\host
MANUALLY LOADING WITH A STARTUP FILE
To load the MFC NLM using a Startup file, you must know the location of
the MFC NLM and the startup file. You must also have edited the startup
file to fit your network environment.
Syntax: load [server/volume:]ngwmfc @[volume/server:]path\startup file
Sample: load server1/vol1:mfc\ngwmfc @\system\mfc\startup.mfc
AUTOMATICALLY LOADING USING AUTOEXEC.NCF
You can add the loading syntax to AUTOEXEC.NCF so that the MFC NLM loads
automatically each time you bring up the file server. You can enter the
complete load command without the startup file, or you can use the
startup file. Remember that you must down the file server and bring it
back up before AUTOEXEC.NCF loads the NLM. Make sure you test the loading
syntax at the console prompt before you add it to AUTOEXEC.NCF.
THE MFC OPERATION SCREEN
When the MFC NLM has been successfully loaded, the MFC Operation
screen appears. The MFC Operation screen is divided into the
following sections:
■ Information/Statistics
■ Logging
■ Interface menu
INFORMATION/STATISTICS
This section displays the name and description assigned to the MFC NLM
through the Admin program and the name of the GroupWise 4.x domain it
is servicing.
UPTIME: This field displays the length of time the NLM has
been running.
PROCESSING: This field displays a rotating bar used to indicate
that the NLM is currently running.
INCOMING PROCESS: This field indicates the MFC NLM's processing
state for incoming WP Office 3.1 messages. It toggles between
ACTIVE and CLOSED.
OUTGOING PROCESS: This field indicates the MFC NLM's processing
state for outgoing GroupWise 4.x messages. It toggles between
ACTIVE and CLOSED.
INCOMING MESSAGES: This field displays the number of messages that
have arrived from the WP Office 3.1 system.
OUTGOING MESSAGES: This field displays the number of messages that
have been sent to the WP Office 3.1 system.
LOGGING
This section displays the tasks performed by the NLM. The amount of
detail displayed here is determined by the logging level. The default
logging level is set using Admin. You can override the default
setting by using the /loglevel switch or by using the Options menu.
See INTERFACE MENU for more information.
The data displayed on the screen is also written to the log file.
INTERFACE MENU
The interface menu is found on the bottom line of the MFC Operation
Screen. The options are:
F7-EXIT: Press F7 to unload the NLM. When the NLM is unloaded,
messages will no longer be converted.
F9-BROWSE LOG FILES: Press F9 to display the current log file in
a NetWare viewing window. You can scroll this window from top to
bottom.
F10- OPTIONS: Press F10 to display the Options Menu which provides
the following options:
VIEW LOG FILE: This option displays a list of all log files that
reside on the disk. You can view any file that is displayed.
CONFIGURE: This option lets you change the defaults that were
set using Admin or the startup switches. These changes take
effect immediately; they remain active until you change them
again or until you unload the NLM. The following settings can
be changed:
LOG LEVEL: Use this option to change the logging level.
MAX LOG AGE: Use this option to change the length of time
the log files are stored on the disk.
MAX DISK SPACE: Use this option to control how much space
the log files can use until the older ones are deleted.
EDIT STARTUP FILE: This option displays only if you loaded the
NLM using a startup file. It lets you change the switch settings.
These changes will take effect after you unload the NLM and load
it using the edited startup file.